Registry module
EMu is a flexible and extensible application that can be customised with relative ease to suit an institution's requirements. Almost anything can be customised from the fields a user is able to view and search, to the uniqueness of a field or combination of fields. The key to EMu's flexibility is its Registry, which stores System configuration information and provides a mechanism for configuring and customising EMu without the need to reprogram the application. It is used to define site-specific configuration parameters such as:
- EMu's security system, including user and group permissions
- System settings, including locale information and file locations
- MIME types for multimedia resources and conversion information for text-based documents
- Mandatory fields
- Lookup List permissions
- Sort options
- Tab order and display
- Languages in use and general language settings
- Unique values
- Order and appearance of tabs in different modes, e.g. New, Search
- Spell checking options
Registry settings are assigned in a module with a user-friendly interface much like that of any other EMu module.
The Registry module is accessed by clicking in the EMu Command Centre. By default it is only accessible to a user with an Administrator account, although Administrators can authorise other users to access the Registry module and to add and edit Registry entries.
Similar to the Windows Registry, EMu's Registry is a database of configuration entries that comprise a hierarchical key structure with a value:
On the left is a hierarchical sequence of keys with a value entered on the right. There may be up to ten keys in the hierarchy, although most Registry entries use only the first four or five. The value tells EMu which permission, condition or value to apply for the specific circumstance described by the sequence of keys.
Tab |
Key |
Description |
---|---|---|
Registry
|
Key |
There may be up to ten keys in the hierarchy, although most Registry entries use only the first four or five. |
Levels |
Indicates how many levels are used in the Registry setting. |
|
Owner |
Username of the person who created the Registry setting. |
|
value |
The value tells EMu which permission, condition or value to apply for the specific circumstance described by the sequence of keys. Values are separated by a semicolon or each value is on a new line. |
Although there is only one value for each Key sequence, the value can comprise multiple entries. In the example above, the value is a list of permissions. In the Registry module, the values are entered one per line. In the back-end such multi-value entries are recorded as a string with each value separated by a ; (semicolon) by default, e.g.:
eaccessionlots;eadmin;ebibliography;ecatalogue;econdition;econservation;eevents;einsurance;einternalecatalogue
Almost every operation a user performs in EMu triggers a Registry entry lookup. This occurs behind the scenes and defines what action the System should take depending on the user's privileges, or the System settings.
While there are potentially hundreds of entries to be made in the Registry, for the most part the EMu Administrator only needs to be concerned with two types of Registry entries: System Settings and Table and Column Settings.
Tip: For details about how the Registry works and how to set Registry settings see The EMu Registry.
Tab | Description |
---|---|
Notes |
See Notes tab for details. |
Security |
See Security tab for details. |
Audit |
See Audit tab for details. |
Admin |
See Admin tab for details. |
Note: Options available on the Registry tab in the Ribbon enable Administrators to copy the Registry entries associated with an existing group or user to a new group or user. Details here.